Support loading custom SQLite extensions#72
Merged
Merged
Conversation
|
@LucDeCaf is this still planned work? |
Collaborator
Hey @graydonpleasants, we pinged you on the original github issue about testing our fix but that may have slipped through the notification void. You are welcome to test the dev release here. Please let us know if that resolves your issue. |
Chriztiaan
previously approved these changes
Jun 4, 2026
Chriztiaan
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wires up the existing
MDSQLiteOptions.Extensionssetting, which allows for loading custom sqlite3 extensions on PowerSync-managed connections. Also adds a flagMDSQLiteOptions.LoadPowerSyncExtensionthat changes if the default core extension is loaded or not, which is useful for platforms which place thepowersynclibrary in a nonstandard location (eg. issue #71).